Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
tyssejc
force-pushed
the
changeset-release/main
branch
from
cdd3769 to
c6f650f
Compare
github-actions
bot
force-pushed
the
changeset-release/main
branch
from
c6f650f to
5582909
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
@junctionjs/core@0.3.0
Minor Changes
#12
cc7d872Thanks @tyssejc! - feat(core): add consent queue guardrails — maxQueueSize, queue:drop telemetry, flush() drains queuemaxQueueSizeoption toConsentConfig— drops oldest events when exceededqueue:dropevents with{ count, reason }when events are lost to timeout or overflowflush()now drains the consent queue for permitted events, critical for page unload@junctionjs/astro@2.0.0
Patch Changes
cc7d872]:@junctionjs/auto-collect@0.1.3
Patch Changes
cc7d872]:@junctionjs/client@0.1.3
Patch Changes
cc7d872]:@junctionjs/cmp-onetrust@2.0.0
Patch Changes
cc7d872]:@junctionjs/debug@2.0.0
Patch Changes
cc7d872]:@junctionjs/destination-amplitude@2.0.0
Patch Changes
cc7d872]:@junctionjs/destination-ga4@2.0.0
Patch Changes
#11
7c8cb06Thanks @tyssejc! - Fix gtag.js integration: use Arguments object instead of Array for dataLayerThe gtag stub function was using an arrow function with rest parameters, which
pushed plain Arrays to the dataLayer. gtag.js silently ignores array entries —
it expects the Arguments object. Switched to a named function declaration using
argumentsto match Google's official snippet.Also added
gtag("consent", "default", {...})call beforegtag("config", ...)when consent mode is enabled. Without this, gtag.js doesn't know consent mode
is active and consent state is never communicated to Google.
Updated dependencies [
cc7d872]:@junctionjs/destination-http@2.0.0
Patch Changes
cc7d872]:@junctionjs/destination-meta@2.0.0
Patch Changes
cc7d872]:@junctionjs/destination-plausible@2.0.0
Patch Changes
cc7d872]:@junctionjs/gateway@0.1.3
Patch Changes
cc7d872]:@junctionjs/next@2.0.0
Patch Changes
cc7d872]: